Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

modern-whs-thesis:0.3.0 #1777

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

modern-whs-thesis:0.3.0 #1777

wants to merge 1 commit into from
+1,394 −0

Conversation

alex289
Copy link
Contributor

@alex289 alex289 commented Feb 20, 2025

I am submitting

  • a new package
  • an update for a package

Description: Update used package versions and make it compatible with Typst 0.13.0

I have read and followed the submission guidelines and, in particular, I

  • selected a name that isn't the most obvious or canonical name for what the package does
  • added a typst.toml file with all required keys
  • added a README.md with documentation for my package
  • have chosen a license and added a LICENSE file or linked one in my README.md
  • tested my package locally on my system and it worked
  • excluded PDFs or README images, if any, but not the LICENSE
  • ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

@typst-package-check typst-package-check bot added the update A package update. label Feb 20, 2025
@alex289
Copy link
Contributor Author

alex289 commented Feb 20, 2025 •
edited
Loading

Mmh the warnings which make the check fail comes from the package codly. Is this a problem?

Dherse/codly#65

@elegaanz
Copy link
Member

Given that a new codly release should happen soon to fix the issue, I would advise to wait for it. But if you want to get this merged now, it would be nice if you released v0.3.1 to update codly once the new version is out. Let me know what you prefer.

@alex289
Copy link
Contributor Author

alex289 commented Feb 20, 2025

Given that a new codly release should happen soon to fix the issue, I would advise to wait for it. But if you want to get this merged now, it would be nice if you released v0.3.1 to update codly once the new version is out. Let me know what you prefer.

Hey, I didn't think the author will fix this so soon so I think I can wait 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
update A package update.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@alex289 @elegaanz